Great job @lucasnewman, I love the speed! 🚀

The mimi codec will be really useful for some models on our roadmap.

FYI, there is an existing repo you can take inspiration from:

https://github.com/senstella/csm-mlx

I will help out when I return from vacation this coming week.

Thanks for the reference! Basic audio gen is working now -- here's a sample.

@Blaizzy I don't know if you want to use the (unquantized) model I uploaded to HF or another repo -- it's up to you! This is what the output looks like:

Model: lucasnewman/csm-1b-mlx
Text: Hello from Sesame.
Voice: af_heart
Speed: 1.0x
Language: a
==========
Audio generated successfully, saving to audio!
==========
Duration:              00:00:01.280
Samples/sec:           18930.8
Prompt:                33 tokens, 20.3 tokens-per-sec
Audio:                 30720 samples, 18930.8 samples-per-sec
Real-time factor:      1.27x
Processing time:       1.62s

The voice, speed, & language aren't applicable here but I was trying to be as surgical as possible with the model loading / generate changes. Feel free to change it up to whatever you'd like.

This is phenomenal @lucasnewman, you crushed it! 🔥

I will review and merge tomorrow. As well as, handle the quantization.

@Blaizzy I don't know if you want to use the (unquantized) model I uploaded to HF or another repo -- it's up to you! This is what the output looks like:

Could you upload your copy to mlx-community with the name:
mlx-community/csm-1b-bf16

and update path utils.py

The voice, speed, & language aren't applicable here but I was trying to be as surgical as possible with the model loading / generate changes. Feel free to change it up to whatever you'd like.

I'm thinking about a general API design. For instance, in my view ref_audio == voice, just that depending on the model it will alternate between text and a path to an audio. But I will save refactoring to v0.1.0 when we get STS up and running.

Could you upload your copy to mlx-community with the name: mlx-community/csm-1b-bf16

The base model is fp32, not bf16, so I'll put it at mlx-community/csm-1b 👍

I'm thinking about a general API design. For instance, in my view ref_audio == voice, just that depending on the model it will alternate between text and a path to an audio. But I will save refactoring to v0.1.0 when we get STS up and running.

Yep, that makes sense. We'll need some kind of voice_caption / voice_text parameter for Sesame and models like F5-TTS, since they require the caption alongside the reference audio.

Could you upload your copy to mlx-community with the name: mlx-community/csm-1b-bf16

The base model is fp32, not bf16, so I'll put it at mlx-community/csm-1b 👍

Sure, that makes sense.

I'm used to converting it to bf16.

I'm thinking about a general API design. For instance, in my view ref_audio == voice, just that depending on the model it will alternate between text and a path to an audio. But I will save refactoring to v0.1.0 when we get STS up and running.

Yep, that makes sense. We'll need some kind of voice_caption / voice_text parameter for Sesame and models like F5-TTS, since they require the caption alongside the reference audio.

Got it, let me check a few things and come back with some suggestions

Merged! 🚀